@chubsta You can get additional info on SVG and ES here.

@Scannigan: I'm with @Keigan on this one.

Before you do any coding, sketch a rough layout of how you want the theme to look. You can start with simple pencil and paper to get the basic layout of elements, or use a design tool such as Photoshop, GIMP, Paint.net, Inkscape, Illustrator, etc.

Here are some simple basics. There are 4 main Views:

System Carousel with System Logos Basic Gamelist System Logo Detailed Gamelist System Logo Metadata (image, description, rating, genre, etc) Video Same as Detailed View, but with a Video instead of an Image

You don't need to support the Video View if you don't want to. Chances are, if other people like your theme, there will be someone out there that will add the Video support for you.

Start by working out what elements you want to show on each View.

The Basic View is pretty rigid, but you can add System specific images like controllers and consoles if you want. The System View used to be pretty set, but now you can style the Carousel to look however you want. Check out the BaseVid theme in the Toolkit as an example. As with the Basic View, you can also add extra images to each System if you want. With the Detailed View, you don't have to show all the metadata if you don't want to. Maybe you don't care about number of times played, or the name of the publisher. You can hide any info you don't want to show.

Now just draw some rectangles. For the Detailed View as an example, maybe you want the Gamelist on the right of the screen, so you draw a rectangle on the right of the screen. You might want a big image in the middle, so draw a big rectangle in the middle. Maybe you want the System Logo under the Gamelist, so you shorten the Gamelist a little and draw a smaller rectangle under it.

Keep going until you have a layout that you like the look of. If you are using pencil and paper, now might be the time to move to a computer program so you can get exact numbers for the <pos> and <size> poperties.

I didn't think of that, thanks @NastyButtler322.

@mattrixk Ah thanks.

:)-

@mattrixk Sweet! More to play with!!

No problem, it may not have worked anyway.

@herb_fargus said in <feature supported="carousel"> Not Working:

the binary release for the toolkit draft includes the latest binary release jdrassa posted.

That isn't up on the toolkit yet is it? I confused myself will too many versions of ES, trying to make sure everything worked with as many versions as possible. I've fixed up BaseVid to use maxSize instead of size for the videos, and fixed the sizing so it looks okay when using logos instead of mix images. I still need to change the gamelists in the repo though.

Edit I have updated the gamelists to use the Logo image instead of the Mix image on Video View. Detailed View still uses the full Mix image.

@chubsta Themes are pretty standard. All you need to do is edit the nameoftheme.xml andtheme.xml file inside each system folder and have it point to the appropriate image / artwork. You can also change colour, transparency, font, position, size etc. It's really easy to do if you are logical and ensure everything points to the correct folder.

I have isolated the issue, while it generates an error code, I am not sure that it is really causing any issues except populating the log. In my theme i do not use the <feature supported="video"> to include video into my theme. Instead I simply create view named <view name="md_video"> similar to any image view. What this has allowed me to do is have the video show if a video is present in the games list, and an image show if no video is available. When i put the "Feature" into the theme, I no longer get an image if a video is not present. I get a black screen, or i can point to a single file as a <default>file.mpv</default> I tested this theory on the recently updated carbon theme and replicated the exact same results. I am going to start a new thread in the themes topic to see if there are any thoughts on this, now that i don't actually have an issue that needs resolved here. Thanks

@jdrassa and @herb_fargus once I sorted out the dlls the 32bit version works well. So maybe sticking with that could be ok as long as we have the info here about making sure a user has 32bit versions of the dlls available. If that works I can record a quick step by step and post it into this thread if the question comes up again no problem.

Or is it possible to include the 32bit vcruntime140 and msvcp140 dlls in the zipped bundle? Not sure if there are legal issues with doing so; if not that could help too.